Method, apparatus and system for procrssing payment request for virtual commodities on open network platform

ABSTRACT

A method, apparatus and system for processing a payment request for a virtual commodity on an open network platform are provided. The method includes: receiving a payment request that is sent by a third-party application server according to a request from a terminal, the payment request carrying at least an account identifier; deducting a charge from an account corresponding to the account identifier according to a payment attribute corresponding to the account identifier; and sending a charge deduction result corresponding to the account to the terminal via the third-party application server. According to the present method, usage rate of network and system resources is improved.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation application of U.S. patent application Ser. No. 16/428,949, filed on May 31, 2019. U.S. application Ser. No. 16/428,949 is a continuation application of U.S. patent application Ser. No. 14/807,324, filed on Jul. 23, 2015 and issued on Jul. 16, 2019 as U.S. Pat. No. 10,354,244. U.S. patent application Ser. No. 14/807,324 is a continuation application of PCT Patent Application No. PCT/CN2013/089860, filed on Dec. 18, 2013, which claims priority to Chinese Patent Application No. 201310038926.5, filed before Chinese Patent Office on Jan. 31, 2013 and entitled “METHOD, APPARATUS AND SYSTEM FOR PROCESSING PAYMENT REQUEST FOR VIRTUAL COMMODITIES ON OPEN NETWORK PLATFORM”, the entire contents of all the above-mentioned applications are incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates to the field of Internet technologies, and in particular, to a method, apparatus and system for processing a payment request for virtual commodities on an open network platform.

BACKGROUND

With the rapid development of network technologies, the Internet is gradually becoming an indispensable part of more and more people's lives. With the continuous development of the Internet, a large number of various open network platforms (hereafter also referred to as open platforms or open network platforms) come out on the Internet, such as a Social Networking Services (SNS) website. A variety of network applications are provided to a user on an open network platform. The user may use a corresponding network service, such as online game, online book, or online video, by using the network applications.

A network application may involve some chargeable items, such as chargeable props, books charged by chapter, or videos charged by episode. In the prior art, payment for a network application-related product is made in the following procedure: a third-party application server sends a payment request to an open platform server upon receiving a purchase request sent by a terminal; the open platform server returns a uniform/universal resource locator (URL) to the application server upon receiving the payment request; the third-party application server instructs the terminal to invoke a corresponding application programming interface (API) to display a payment page; the user, after confirming corresponding information, clicks the OK button to instruct the open platform server to deduct a charge, i.e., deduct virtual currency from the corresponding account; and the open platform server, upon successfully deducting the charge, instructs the delivery server to perform a delivery process.

During the implementation of the present disclosure, the inventors find that the prior art has at least the following problems:

During a conventional payment process with respect to a network application-related product, a payment page needs to be popped up on the terminal; afterwards, the user cannot operate on an undergoing application interface, or even cannot see the application interface. The user needs to confirm information on the payment page, and return to the undergoing application interface by clicking the OK button. For example, the user purchases a book-reading application by chapter, and imposes a higher requirement on continuity in book reading. In this case, during purchase of a next chapter, the user generally desires to directly make a payment and quickly and sequentially read the content in the next chapter. If a payment page is popped up forcibly, continuity of the user's reading is interrupted and hence payment willing is reduced. Still for example, during item purchase during multi-role gaming, forcible pop-up of a payment page causes interruption and disturb to users playing such games. With respect to such applications, if a payment page is popped up during use of the applications, normal operations of the users in the applications are affected, tending to cause misoperations. In case of misoperations, the users may need to perform correct operations again to achieve their originally desired objectives. However, such repeated operations cause repeated occupation of network and system resources, thereby resulting in a waste of network and system resources.

SUMMARY

To address the above technical problems, embodiments of the present disclosure provide a method, apparatus and system for processing a payment request for a virtual commodity on an open network platform, to improve usage rate of network and system resources. The technical solutions are as follows:

In a first aspect, an embodiment of the present disclosure provides a method for processing a payment request for a virtual commodity on an open network platform. The method includes: receiving a payment request that is sent by a third-party application server according to a request from a terminal, the payment request carrying at least an account identifier; deducting a charge from an account corresponding to the account identifier according to a payment attribute corresponding to the account identifier; and sending a charge deduction result corresponding to the account to the terminal via the third-party application server.

In a second aspect, an embodiment of the present disclosure provides an apparatus for processing a payment request for a virtual commodity on an open network platform. The apparatus includes: a receiving module, configured to receive a payment request that is sent by a third-party application server according to a request from a terminal, the payment request carrying at least an account identifier; a charge deducting module, configured to deduct a charge from an account corresponding to the account identifier according to a payment attribute corresponding to the account identifier; and a notifying module, configured to send a charge deduction result corresponding to the account to the terminal via the third-party application server.

In a third aspect, an embodiment of the present disclosure provides a system for processing a payment request for a virtual commodity on an open network platform. The system includes: an open platform server, a third-party application server, and at least one terminal.

The third-party application server is configured to: send a payment request to the open platform server according to a request of the terminal, the payment request carrying at least an account identifier; and upon receiving a charge deduction result sent by the open platform server, send the deduction result to the terminal.

The open platform server is configured to: upon receiving the payment request, deduct a charge from an account corresponding to the account identifier according to a payment attribute corresponding to the account identifier; and send a deduction result corresponding to the account to the third-party application server.

The technical solutions provided in the embodiments of the present disclosure achieve the following beneficial effects:

According to the embodiments of the present disclosure, a corresponding account is determined according to an account identifier carried in a payment request, a charge is deducted from the account according to a payment attribute of the account, and a charge deduction result is sent to a terminal via a third-party application server. With respect to different payment attributes of different terminals, different charge deduction methods may be employed, thereby preventing a traditional charge deduction method where payment and charge deduction are implemented only on a pop-up payment page. In this way, misoperations caused due to the pop-up page may be prevented, and usage rate of network and system resources may be improved.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the technical solutions in the embodiments of the present disclosure, the accompanying drawings for illustrating the embodiments are briefly described below. Apparently, the accompanying drawings in the following description illustrate only some embodiments of the present disclosure, and persons of ordinary skill in the art may derive other accompanying drawings based on these accompanying drawings without any creative efforts.

FIG. 1 is a flowchart of a method for processing a payment request for a virtual commodity on an open network platform according to an embodiment of the present disclosure;

FIG. 2 is a flowchart of a method for processing a payment request for a virtual commodity on an open network platform according to an embodiment of the present disclosure;

FIG. 3 is a flowchart of a method for processing a payment request for a virtual commodity on an open network platform according to an embodiment of the present disclosure;

FIG. 4 is a flowchart of a method for processing a payment request for a virtual commodity on an open network platform according to an embodiment of the present disclosure;

FIG. 5 is a flowchart of a method for processing a payment request for a virtual commodity on an open network platform according to an embodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of an apparatus for processing a payment request for a virtual commodity on an open network platform according to an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of a system for processing a payment request for a virtual commodity on an open platform server according to an embodiment of the present disclosure; and

FIG. 8 is a schematic structural diagram of an open platform server according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

To make the objectives, technical solutions, and advantages of the present disclosure clearer, embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

An embodiment of the present disclosure provides a method for processing a payment request for a virtual commodity on an open network platform. As illustrated in FIG. 1, the method includes the following steps:

step 101: receiving a payment request that is sent by a third-party application server according to a request from a terminal, the payment request carrying at least an account identifier;

step 102: deducting a charge from an account corresponding to the account identifier according to a payment attribute corresponding to the account identifier; and

step 103: sending a charge deduction result corresponding to the account to the terminal via the third-party application server.

According to this embodiment, a corresponding account is determined according to an account identifier carried in a payment request, a charge is deducted from the account according to a payment attribute of the account, and a charge deduction result is sent to a terminal via a third-party application server. With respect to different payment attributes of different terminals, different charge deduction methods may be employed, thereby preventing a traditional charge deduction method where payment and charge deduction are implemented only on a pop-up payment page. In this way, misoperations caused due to the pop-up page may be prevented, and usage rate of network and system resources may be improved.

An embodiment of the present disclosure provides a method for processing a payment request for a virtual commodity on an open network platform. Preferably, an executing subject of the method may be an open platform server. Herein, the virtual commodity may be content presented in a network application, for example, an electronic book, or may be a virtual item used in the network application, for example, a game item, or may be a software product involved in the network application.

The process of processing a payment request for a virtual commodity on an open network platform as illustrated in FIG. 1 is elaborated in detail with reference to specific implementation as follows:

Step 101: An open platform server receives a payment request that is sent by a third-party application server according to a request from a terminal, the payment request carrying at least an account identifier (for example, an account number). The payment request may further carry price information, where the price information may be the sum price of the commodities requested by a user, or may be identifiers, quantities, and unit prices of the commodities purchased by the user, which can be used by the open platform servers to calculate the sum price of the commodities.

Related commodity information may be displayed on a page subsequently displayed to the terminal. Preferably, the payment request may further carry a transaction identifier, for example, a transaction track number. The third-party application server may be a server for application provided by a third party except of the open platform server and the terminal.

Specifically, during use of an application, if the user needs to purchase a virtual commodity therein, the user may click the Purchase button. In this case, the application generates a purchase request, where the request may carry such information as identifiers and quantity of commodities, and the account identifier of the account used by the user, and the information is sent to the third-party application server via the terminal. Upon receiving the purchase request, the third-party application server may record the account identifier carried in the purchase request, and generate a corresponding transaction identifier and price information. The third-party application server may generate a payment request corresponding to the purchase request, where the payment request may carry the account identifier and may further carry the transaction identifier and price information. Subsequently, the generated payment request is sent to the open platform server.

Step 102: The open platform server deducts a charge from an account corresponding to the account identifier according to a payment attribute corresponding to the account identifier. The payment attribute is used to indicate a payment mode currently used by an account. A plurality of payment attributes may be defined in advance, for example, a Do Not Disturb (DND) payment attribute to be described as follows. In the payment mode corresponding to the DND payment attribute, a charge may be deducted with no need of popping up a payment page.

In the method, DND payment attributes may be preset for various accounts on the open platform server. Specifically, an identifier bit recording that the account has the DND payment attribute or does not have the DND payment attribute may be set for each of the accounts. Nevertheless, preferably, the open platform server may record an account identifier of an account having the DND payment attribute, and may be provided with a DND payment account list, where the list records account identifiers of all accounts having the DND payment attribute. The DND payment attribute of the account may be uniformly set by the open platform server, and preferably, may be set by the user by sending a request via terminal. The specific process of setting the DND payment attribute is elaborated as follows.

Step 102 may specifically comprise: the open platform server deducts the charge from the account directly according to the payment request if the account corresponding to the account identifier has a DND payment attribute.

Specifically, upon receiving the payment request, the open platform server may acquire an account identifier carried therein, and query whether the acquired account identifier exists in the account identifiers of the accounts having the DND payment attribute that are recorded in the DND payment account list. If the acquired account identifier exists, the open platform server determines that the corresponding account has the DND payment attribute; otherwise, the open platform server determines that the corresponding account does not have the DND payment attribute.

If the account corresponding to an account identifier has the DND payment attribute, the open platform server may acquire the price information and the account identifier carried in the payment request. If the price information indicates the sum price of the commodities, the open platform server may deduct the sum from account balance of the corresponding account. If the price information indicates the identifiers, quantities, and unit prices of the commodities, the open platform server may calculate the sum price of the commodities according to the information, and deduct the sum from account balance of the corresponding account. The charge deduction herein typically refers to deduction in terms of virtual currency, for example, game currency, Q currency, and the like. To be specific, a transaction initiated by the user is a transaction of purchasing virtual commodities in the network application using virtual currency.

Step 103: The open platform server sends a charge deduction result corresponding to the account to the terminal via the third-party application server. The open platform server may also display the charge deduction result on a third-party application page of the terminal in a floating manner via the third-party application server. The third-party application page may be a display page on a client of the third-party application.

After step 102, the method may further include a step of instructing, by the open platform server, the third-party application server to deliver a commodity to the account corresponding to the account identifier.

Specifically, the open platform server may instruct, by sending a delivery notification to the third-party application server, the third-party application server to perform a delivery process. Upon completion of the delivery, the third-party application server notifies the open platform server that the delivery process is complete. Preferably, the process of instructing the third-party application server to perform a delivery process may be specifically as follows:

Firstly, the open platform server sends a delivery notification carrying a transaction identifier to the third-party application server. Subsequently, the open platform server performs corresponding processing with respect to the following two scenarios:

Scenario 1: Upon receiving a notification success notification carrying a transaction identifier sent by the third-party application server, the open platform server notifies, according to the process illustrated in FIG. 2, the terminal that the transaction is complete. The process may specifically include the following steps:

Step 201: The open platform server sends a transaction complete notification to the third-party application server. The transaction complete notification may carry a result code indicative of a successful DND payment and a URL of a transaction complete notification page.

The open platform server may pre-define a plurality of result codes with the third-party application server. Each of the result codes corresponds to an API. Each API may correspond to a plurality of result codes. These APIs may be preconfigured by the open platform server, and may be notified to the third-party application server. Further, a mapping relationship between result codes and APIs may be notified to the third-party application server. In this way, when the open platform server needs to display an interface-based notification on the terminal, the open platform server may send a corresponding notification to the third-party application server, where the notification may carry a corresponding result code such that the third-party application guides the terminal to invoke the corresponding API to display the interface-based notification.

Prior to sending the notification to the third-party application server, the open platform server may pre-generate related data on the transaction complete notification page that is to be displayed on the terminal, and store the generate data. The stored data may be accessed using the URL.

Step 202: The third-party application server guides the terminal to invoke an API corresponding to the result code to access the URL.

Specifically, the third-party application server may firstly acquire the API corresponding to the result code, and then sends the URL as a parameter of the API to the terminal, such that the terminal invokes the API to access the URL and perform corresponding window rendering. In addition, the third-party application server may also load the related API to the terminal when the terminal starts an application, and during step 202, send the corresponding result code or identifier of the API and the URL to the terminal, such that the terminal uses the URL as the parameter of the API to invoke the corresponding API to access the URL and perform the corresponding window rendering.

The API corresponding to the result code indicative of a successful DND payment may be preferably an API displayed at a floating layer. To be specific, after the API is invoked, the corresponding display window appears in a floating manner from a preset area, displays the corresponding content, and disappears a preset duration later. During the entire display process, user's operations on the application are not affected.

Step 203: Upon detecting that the terminal has accessed the URL, the open platform server sends data on a transaction complete notification page to the terminal.

The data of the transaction complete notification page is stored at the address corresponding to the URL. The data may include notification text indicative of transaction completion and sum price of the commodities, and may further include names, quantities, and unit prices of the commodities. When the terminal accesses the URL, the open platform server sends the data to the terminal for the terminal to display the same.

Scenario 2: Upon detecting that the third-party application server fails in the delivery (the open platform server may preset a response duration; if a delivery success notification has not been received from the third-party application server within the preset response duration after sending a delivery notification, the open platform server determines that the delivery fails; and if receiving a delivery failure notification from the third-party application server, the open platform server also determines that the delivery fails), the open platform server refunds the deducted charge to the account corresponding to the account identifier, and sends a delivery failure notification to the third-party application server according to the process illustrated in FIG. 3. The process may specifically include the following steps:

Step 301: The open platform server sends a delivery failure notification to the third-party application server. The delivery failure notification may carry a result code indicative of a failed delivery and a URL of a delivery failure notification page.

Step 302: The third-party application server guides the terminal to invoke an API corresponding to the result code to access the URL.

Step 303: Upon detecting that the terminal has accessed the URL, the open platform server sends data on a delivery failure notification page to the terminal.

Steps 301-303 are similar to steps 201-203, with difference only in corresponding page data and parameter. Therefore, the specific process may be referenced to steps 201-203, which is not described herein any further.

In addition, the API corresponding to the result code indicative of a delivery failure may also be an API displayed at a floating layer. Nevertheless, for ease of prompt to the user, an API displayed at an upper layer may also be used, where the corresponding display window may be displayed at the upper layer on an application interface, and the application interface is locked at the lower part. In this way, the user may only operate on the window displayed at the upper layer, and may operative on the original application interface after the window displayed at the upper layer is closed.

In step 102, during the charge deduction from the account corresponding to the account identifier carried in the payment request, if the charge deduction fails (a charge deduction failure may be caused due to insufficient balance in the account), the charge deduction failure may be notified to the terminal according to the process illustrated in FIG. 4. The process may specifically include the following steps:

Step 401: The open platform server sends a charge deduction failure notification to the third-party application server. The charge deduction failure notification may carry a result code indicative of a failed charge deduction and a URL of a charge deduction failure notification page.

Step 402: The third-party application server guides the terminal to invoke an API corresponding to the result code to access the URL.

Step 403: Upon detecting that the terminal has accessed the URL, the open platform server sends data on a charge deduction failure notification page to the terminal.

Steps 401-403 are similar to steps 201-203, with difference only in corresponding page data and parameter. Therefore, the specific process may be referenced to steps 201-203, which is not described herein any further.

In addition, the API corresponding to the result code indicative of a charge deduction failure may also be an API displayed at a floating layer. Nevertheless, for ease of prompt to the user, an API displayed at an upper layer may also be used.

In this embodiment, in cases where the account corresponding to an account identifier carried in the payment request has the DND payment attribute, the process may be performed according to step 102; in cases where the account corresponding to an account identifier carried in the payment request does not have the DND payment attribute, the process is performed according to a preset processing manner. The processing manner may be a default one. In addition, the process may be performed according to the manner illustrated in FIG. 5, including the following steps:

Step 501: The open platform server sends a non-DND payment notification to the third-party application server. The non-DND payment notification carries a transaction identifier, a result code indicative of a non-DND payment, and a URL of a payment page.

Step 502: The third-party application server guides the terminal to invoke an API corresponding to the result code to access the URL.

Step 503: Upon detecting that the terminal has accessed the URL, the open platform server sends data on a payment page to the terminal.

Steps 501-503 are similar to steps 201-203, with difference only in corresponding page data and parameter. Therefore, the specific process may be referenced to steps 201-203, which is not described herein any further.

It should be noted that the API corresponding to the result code indicative of a non-DND payment may be preferably an API displayed at an upper layer.

Step 504: Upon receiving a payment confirm notification carrying the transaction identifier sent by the terminal, the open platform server deducts the charge from the corresponding account according to the price information, and instructs, after the charge deduction, the third-party application server to make a delivery.

The open platform server instructs the third-party application server to perform a delivery process and a process with respect to the charge deduction failure. The details may be referenced to the above specific process, which is not described herein any further.

Based on the method for processing a payment request for a virtual commodity on an open network platform, an embodiment of the present disclosure further provides a method for setting a DND payment attribute for an account, where the open platform server pre-records the account identifier of an account having the DND payment attribute. The account identifier may be recorded in a DND payment account list. The method may include the following steps:

First, the open platform server receives a DND payment attribute setting request sent by the terminal or the third-party application server. The DND payment attribute setting request carries an account identifier and corresponding operation information. The operation information may indicate enabling a DND payment or canceling a DND payment.

Before setting a DND payment attribute, the user may send a DND payment attribute setting request to the open platform server via the terminal, or may send a DND payment attribute setting request to the third-party application server, whereupon the third-party application server forwards the request to the open platform server.

Preferably, during steps 201-203, the open platform server may set an option for canceling the DND payment on the transaction complete notification page, and the user may choose whether to cancel the DND payment. If the user chooses to cancel the DND payment, the terminal sends operation information indicating canceling the DND payment to the open platform server as the DND payment attribute setting request.

During steps 501-504, the open platform server may set an option for enabling the DND payment on the payment page, and the user may choose whether to enable the DND payment. If the user chooses to enable the DND payment, the terminal sends operation information indicating enabling the DND payment to the open platform server as the DND payment attribute setting request.

Subsequently, if the operation information indicates enabling the DND payment, the open platform server records the account identifier as the account identifier of the account having the DND payment attribute; and if the operation indicates canceling the DND payment, the open platform server delete the account identifier from the account identifiers of the accounts having the DND payment attribute. Upon completion of the operation, a setting success notification may be sent to the terminal.

According to this embodiment, a corresponding account is determined according to an account identifier carried in a payment request, a charge is deducted from the account according to a payment attribute of the account, and a charge deduction result is sent to a terminal via a third-party application server. With respect to different payment attributes of different terminals, different charge deduction methods may be employed, thereby preventing a traditional charge deduction method where payment and charge deduction are implemented only on a pop-up payment page. In this way, misoperations caused due to the pop-up page may be prevented, and usage rate of network and system resources may be improved.

Based on the same technical concept, an embodiment of the present disclosure provides an apparatus for processing a payment request for a virtual commodity on an open network platform. As illustrated in FIG. 6, the apparatus includes:

a receiving module 610, configured to receive a payment request that is sent by a third-party application server according to a request from a terminal, the payment request carrying at least an account identifier;

a charge deducting module 620, configured to deduct a charge from an account corresponding to the account identifier according to a payment attribute corresponding to the account identifier; and

a notifying module 630, configured to send a charge deduction result corresponding to the account to the terminal via the third-party application server.

Preferably, the notifying module 630 is further configured to display the charge deduction result on a third-party application page of the terminal at a floating layer via the third-party application server.

Preferably, the charge deducting module 620 is configured to:

deduct the charge from the account according to the payment request if the account corresponding to the account identifier has a DND payment attribute.

Preferably, the notifying module 630 is further configured to:

instruct the third-party application server to delivery the commodity to the account corresponding to the account identifier.

Preferably, the payment request further carries a transaction identifier.

The notifying module 630 is configured to:

send a delivery notification carrying the transaction identifier to the third-party application server;

upon receiving a delivery success notification carrying the transaction identifier sent by the third-party application server, send a transaction complete notification to the third-party application server, the transaction complete notification carrying a result code indicative of a successful DND payment and a URL of a transaction complete notification page, such that the third-party application server guides the terminal to invoke an API corresponding to the result code to access the URL; and upon detecting that the terminal has accessed the URL, send data on the transaction complete notification page to the terminal;

upon detecting that the third-party application server fails in the delivery, refund the deducted charge to the account corresponding to the account identifier, and send a delivery failure notification to the third-party application server, the delivery failure notification carrying a result code indicative of a failed delivery and a URL of a delivery failure notification page, such that the third-party application server guides the terminal to invoke an API corresponding to the result code to access the URL; and upon detecting that the terminal has accessed the URL, send data on the delivery failure notification page to the terminal.

Preferably, the API corresponding to the result code indicative of the successful DND payment, and/or the API corresponding to the result code indicative of the failed delivery is an API displayed at a floating layer.

Preferably, the notifying module 630 is further configured to:

send a charge deduction failure notification to the third-party application server, the charge deduction failure notification carrying a result code indicative of a failed charge deduction and a URL of a charge deduction failure notification page, such that the third-party application server guides the terminal to invoke an API corresponding to the result code to access the URL; and upon detecting that the terminal has accessed the URL, send data on the charge deduction failure notification page to the terminal.

Preferably, the apparatus further includes a recording module, configured to:

pre-record the account identifier of the account having the DND payment attribute.

Preferably, the recording module is further configured to:

receive a DND payment attribute setting request sent by the terminal or the third-party application server, the DND payment attribute setting request carrying the account identifier and corresponding operation information;

if the operation information indicates enabling a DND payment, record the account identifier as the account identifier of the account having the DND payment attribute;

if the operation information indicates canceling a DND payment, delete the account identifier from the recorded account identifiers of the accounts having the DND payment attribute.

According to this embodiment, a corresponding account is determined according to an account identifier carried in a payment request, a charge is deducted from the account according to a payment attribute of the account, and a charge deduction result is sent to a terminal via a third-party application server. With respect to different payment attributes of different terminals, different charge deduction methods may be employed, thereby preventing a traditional charge deduction method where payment and charge deduction are implemented only on a pop-up payment page. In this way, misoperations caused due to the pop-up page may be prevented, and usage rate of network and system resources may be improved.

Based on the same technical concept, an embodiment of the present disclosure provides a system for processing a payment request for a virtual commodity on an open network platform. As illustrated in FIG. 7, the system includes an open platform server 710, a third-party application server 720, and at least one terminal 730.

The third-party application server 720 is configured to: send a payment request to the open platform server 710 according to a request of the terminal 730, the payment request carrying at least an account identifier; and upon receiving a charge deduction result sent by the open platform server 710, send the deduction result to the terminal 730.

The open platform server 710 is configured to: upon receiving the payment request, deduct a charge from an account corresponding to the account identifier according to a payment attribute corresponding to the account identifier; and send a deduction result corresponding to the account to the third-party application server 720.

According to this embodiment, a corresponding account is determined according to an account identifier carried in a payment request, a charge is deducted from the account according to a payment attribute of the account, and a charge deduction result is sent to a terminal via a third-party application server. With respect to different payment attributes of different terminals, different charge deduction methods may be employed, thereby preventing a traditional charge deduction method where payment and charge deduction are implemented only on a pop-up payment page. In this way, misoperations caused due to the pop-up page may be prevented, and usage rate of network and system resources may be improved.

FIG. 8 is a schematic structural diagram of a server according to an embodiment of the present disclosure (the server may serve as the open platform server). The server 1900 may function differently depending on configuration or performance, and may include at least one central processing unit (CPU) 1922 (for example, at least one processor), a memory 1932, at least one storage medium 1930 (for example, at least one mass storage device) for storing an application procedure 1942 or data 1944. The memory 1932 and the non-transitory storage medium 1930 may be used for non-transitory storage or permanent storage. Programs stored in the storage medium 1930 may include at least one module (now shown in the drawing), where each module may include a series of operation instructions to be executed on the server. Further, the CPU 1922 may be set as communicating with the storage medium 1930, and executing the operation instructions included in the storage medium 1930 on the server 1900.

The server 1900 may further include at least one power supply 1926, at least one wired or wireless network interface 1950, at least one input/output interface 1958, at least one keyboard 1956, and/or at least one operating system 1941, for example, Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, and the like.

The server 1900 may include a memory and at least one program, where the at least one program is stored in the memory, and is configured to be executed by at least one processor. The at least one program includes instructions for performing the following operations:

receiving a payment request that is sent by a third-party application server according to a request from a terminal, the payment request carrying at least an account identifier;

deducting a charge from an account corresponding to the account identifier according to a payment attribute corresponding to the account identifier; and

sending a charge deduction result corresponding to the account to the terminal via the third-party application server.

Preferably, the at least one program further includes an instruction for performing the following operation:

displaying the charge deduction result on a third-party application page of the terminal at a floating layer via the third-party application server.

Preferably, the deducting a charge from an account corresponding to the account identifier according to a payment attribute corresponding to the account identifier includes:

deducting the charge from the account according to the payment request if the account corresponding to the account identifier has a DND payment attribute.

Preferably, the at least one program further includes an instruction for performing the following operation:

instructing the third-party application server to delivery the commodity to the account corresponding to the account identifier.

Preferably, the payment request further carries a transaction identifier:

the instructing the third-party application server to delivery the commodity to the account corresponding to the account identifier includes:

sending a delivery notification carrying the transaction identifier to the third-party application server;

upon receiving a delivery success notification carrying the transaction identifier sent by the third-party application server, sending a transaction complete notification to the third-party application server, the transaction complete notification carrying a result code indicative of a successful DND payment and a URL of a transaction complete notification page, such that the third-party application server guides the terminal to invoke an API corresponding to the result code to access the URL; and upon detecting that the terminal has accessed the URL, sending data on the transaction complete notification page to the terminal;

upon detecting that the third-party application server fails in the delivery, refunding the deducted charge to the account corresponding to the account identifier, and sending a delivery failure notification to the third-party application server, the delivery failure notification carrying a result code indicative of a failed delivery and a URL of a delivery failure notification page, such that the third-party application server guides the terminal to invoke an API corresponding to the result code to access the URL; and upon detecting that the terminal has accessed the URL, sending data on the delivery failure notification page to the terminal.

Preferably, the API corresponding to the result code indicative of the successful DND payment, and/or the API corresponding to the result code indicative of the failed delivery is an API displayed at a floating layer.

Preferably, the at least one program further includes instructions for performing the following operations:

sending a charge deduction failure notification to the third-party application server, the charge deduction failure notification carrying a result code indicative of a failed charge deduction and a URL of a charge deduction failure notification page, such that the third-party application server guides the terminal to invoke an API corresponding to the result code to access the URL; and upon detecting that the terminal has accessed the URL, sending data on the charge deduction failure notification page to the terminal.

Preferably, the at least one program further includes an instruction for performing the following operation:

pre-recording the account identifier of the account having the DND payment attribute.

Preferably, the at least one program further includes instructions for performing the following operations:

receiving a DND payment attribute setting request sent by the terminal or the third-party application server, the DND payment attribute setting request carrying the account identifier and corresponding operation information;

if the operation information indicates enabling a DND payment, recording the account identifier as the account identifier of the account having the DND payment attribute;

if the operation information indicates canceling a DND payment, deleting the account identifier from the recorded account identifiers of the accounts having the DND payment attribute.

According to this embodiment, a corresponding account is determined according to an account identifier carried in a payment request, a charge is deducted from the account according to a payment attribute of the account, and a charge deduction result is sent to a terminal via a third-party application server. With respect to different payment attributes of different terminals, different charge deduction methods may be employed, thereby preventing a traditional charge deduction method where payment and charge deduction are implemented only on a pop-up payment page. In this way, misoperations caused due to the pop-up page may be prevented, and usage rate of network and system resources may be improved.

It should be noted that, during processing of a payment request, the apparatus for processing a payment request for a virtual commodity on an open network platform according to the embodiment of the present disclosure is described by only using division of the above functional modules as an example. In practice, the functions may be assigned to different functional modules for implementation as required. To be specific, the internal structure of the apparatus is divided into different functional modules to implement all or part of the above-described functions. Furthermore, the apparatus for processing a payment request for a virtual commodity on an open network platform is based on the same inventive concept as the method for processing a payment request for a virtual commodity on an open network platform according to the embodiments of the present disclosure. The specific implementation is elaborated in the method embodiments, which is not described herein any further.

The sequence numbers of the preceding embodiments of the present disclosure are only for ease of description, but do not denote the preference of the embodiments.

Persons of ordinary skill in the art should understand that all or part of steps of the preceding methods may be implemented by hardware or hardware following instructions of programs. The programs may be stored in a non-transitory computer-readable storage medium, and may be executed by at least one processor. The storage medium may be a read only memory, a magnetic disk, or a compact disc-read only memory.

Described above are merely preferred embodiments of the present disclosure, but are not intended to limit the present disclosure. Any modification, equivalent replacement, or improvement made without departing from the spirit and principle of the present disclosure should fall within the protection scope of the present disclosure. 

What is claimed is:
 1. A method for processing a payment request for a virtual commodity on an open network platform, comprising: executing, by a user terminal, a third-party application on a graphical user interface; receiving, by the user terminal, a payment request of the virtual commodity based on a user input on the graphical user interface; sending, by the user terminal, the payment request to the open network platform via a third-party application server corresponding to the third-party application, the payment request carrying at least an account identifier such that the open network platform determines whether the account identifier has a Do Not Disturb (DND) payment attribute by querying an account list based on the account identifier; in response to determining that the account identifier has the DND payment attribute, receiving, from the open network platform via the third-party application server, a charge deduction result corresponding to a user account of the account identifier without receiving a payment page to be displayed that requests a user payment confirmation, the charge deduction result being obtained by directly deducting a charge from the user account corresponding to the account identifier on the open network platform; invoking, by the user terminal, an application programming interface (API) associated with the charge deduction result to render a first window of the charge deduction result; and displaying, by the user terminal, the first window in a floating layer on the graphical user interface associated with the third-party application such that user operations on the third-party application is not affected during a process of displaying the first window.
 2. The method according to claim 1, further comprising: sending a DND payment attribute setting request to the open network platform via the third-party application server, the DND payment attribute setting request carrying the account identifier and corresponding operation information received by the user terminal based on a user setting operation; wherein: if the operation information indicates enabling a DND payment, the account identifier is recorded by the open network platform as the account identifier of the user account having the DND payment attribute; and if the operation information indicates canceling a DND payment, the account identifier is deleted by the open network platform from the account list of the recorded account identifiers having the DND payment attribute.
 3. The method according to claim 1, wherein invoking the API associated with the charge deduction result comprises: predefining a plurality of result codes indicating a plurality of payment request processing results with the third-party application server; preconfiguring mapping relationships between the plurality of result codes and APIs, each result code corresponds to one of the APIs; receiving an interface-based notification carrying to a corresponding result code sent by the open platform and forwarded by the third-party application server, the result code being associated with the charge deduction result; invoking the corresponding API to display the interface-based notification on the graphical user interface.
 4. The method according to claim 1, further comprising: receiving, from the third-party application server, delivery of the virtual commodity to the user account corresponding to the account identifier.
 5. The method according to claim 4, wherein the payment request further carries a transaction identifier; and receiving, from the third-party application server, delivery of the virtual commodity to the user account corresponding to the account identifier comprises: receiving a uniform resource locator (URL) of a transaction complete notification page from the third-party application server after the third-party application server sends a delivery success notification carrying the transaction identifier to the open network platform and receives a transaction complete notification from the open network platform, the transaction complete notification carrying a result code indicative of a successful DND payment the URL of the transaction complete notification page; invoking a first API corresponding to the result code indicative of the successful DND payment to access the URL of the transaction complete notification page; and after the user terminal has accessed the URL of the transaction complete notification page, receiving data on the transaction complete notification page.
 6. The method according to claim 4, wherein the payment request further carries a transaction identifier; and receiving, from the third-party application server, delivery of the virtual commodity to the user account corresponding to the account identifier comprises: receiving a URL of a delivery failure notification page from the third-party application server after the third-party application server fails in the delivery and the open network platform refunds the deducted charge to the user account corresponding to the account identifier and sends a delivery failure notification to the third-party application server, the delivery failure notification carrying a result code indicative of a failed delivery and the URL of the delivery failure notification page; invoking a second API corresponding to the result code indicative of the failed delivery to access the URL of the delivery failure notification page; and after the user terminal has accessed the URL of the delivery failure notification page, receiving data on the delivery failure notification page.
 7. The method according to claim 1, further comprising: receiving a URL of a charge deduction failure notification page from the third-party application server after the third-party application server receives a charge deduction failure notification from the open network platform, the charge deduction failure notification carrying a result code indicative of a failed charge deduction and the URL of the charge deduction failure notification page; invoking a third API corresponding to the result code indicative of the failed charge deduction to access the URL of the charge deduction failure notification page; and after the user terminal has accessed the URL, receiving data on the charge deduction failure notification page.
 8. The method according to claim 1, further comprising: in response to determining that the account identifier does not have the DND payment attribute, receiving a URL of a payment page from the third-party application server after the third-party application server receives a non-DND payment notification from the open network platform, the non-DND payment notification carrying a transaction identifier, a result code indicative of a non-DND payment, and the URL of the payment page; invoking a fourth API corresponding to the result code indicative of the non-DND payment to access the URL of the payment page; and after the user terminal has accessed the URL, sending a payment confirmation notification carrying the transaction identifier based on user input on the payment page displayed in the graphical user interface of the third-party application, such that the open network platform deducts a charge from the user account corresponding to the account identifier.
 9. The method according to claim 8, wherein invoking the fourth API corresponding to the result code indicative of the non-DND payment comprises: rendering and displaying a second window in an upper layer on graphical user interface of the third-party application; and locking a layer lower than the second window on the graphical user interface, wherein only operation on the second window displayed on the upper layer is accepted by the user terminal until the second window is closed.
 10. A user terminal for processing a payment request for a virtual commodity on an open network platform, comprising: a memory; and a processor coupled to the memory and configured to perform: executing a third-party application on a graphical user interface; receiving a payment request of the virtual commodity based on a user input on the graphical user interface; sending the payment request to the open network platform via a third-party application server corresponding to the third-party application, the payment request carrying at least an account identifier such that the open network platform determines whether the account identifier has a Do Not Disturb (DND) payment attribute by querying an account list based on the account identifier; in response to determining that the account identifier has the DND payment attribute, receiving, from the open network platform via the third-party application server, a charge deduction result corresponding to a user account of the account identifier without receiving a payment page to be displayed that requests a user payment confirmation, the charge deduction result being obtained by directly deducting a charge from the user account corresponding to the account identifier on the open network platform; invoking an application programming interface (API) associated with the charge deduction result to render a first window of the charge deduction result; and displaying the first window in a floating layer on the graphical user interface associated with the third-party application such that user operations on the third-party application is not affected during a process of displaying the first window.
 11. The user terminal according to claim 10, wherein invoking the API associated with the charge deduction result comprises: predefining a plurality of result codes indicating a plurality of payment request processing results with the third-party application server; preconfiguring mapping relationships between the plurality of result codes and APIs, each result code corresponds to one of the APIs; receiving an interface-based notification carrying to a corresponding result code sent by the open platform and forwarded by the third-party application server, the result code being associated with the charge deduction result; invoking the corresponding API to display the interface-based notification on the graphical user interface.
 12. The user terminal according to claim 10, wherein the processor is further configured to perform: receiving, from the third-party application server, delivery of the virtual commodity to the user account corresponding to the account identifier.
 13. The user terminal according to claim 12, wherein the payment request further carries a transaction identifier; and receiving, from the third-party application server, delivery of the virtual commodity to the user account corresponding to the account identifier comprises: receiving a uniform resource locator (URL) of a transaction complete notification page from the third-party application server after the third-party application server sends a delivery success notification carrying the transaction identifier to the open network platform and receives a transaction complete notification from the open network platform, the transaction complete notification carrying a result code indicative of a successful DND payment the URL of the transaction complete notification page; invoking a first API corresponding to the result code indicative of the successful DND payment to access the URL of the transaction complete notification page; and after the user terminal has accessed the URL of the transaction complete notification page, receiving data on the transaction complete notification page.
 14. The user terminal according to claim 12, wherein the payment request further carries a transaction identifier; and receiving, from the third-party application server, delivery of the virtual commodity to the user account corresponding to the account identifier comprises: receiving a URL of a delivery failure notification page from the third-party application server after the third-party application server fails in the delivery and the open network platform refunds the deducted charge to the user account corresponding to the account identifier and sends a delivery failure notification to the third-party application server, the delivery failure notification carrying a result code indicative of a failed delivery and the URL of the delivery failure notification page; invoking a second API corresponding to the result code indicative of the failed delivery to access the URL of the delivery failure notification page; and after the user terminal has accessed the URL of the delivery failure notification page, receiving data on the delivery failure notification page.
 15. The user terminal according to claim 10, wherein the processor is further configured to perform: receiving a URL of a charge deduction failure notification page from the third-party application server after the third-party application server receives a charge deduction failure notification from the open network platform, the charge deduction failure notification carrying a result code indicative of a failed charge deduction and the URL of the charge deduction failure notification page; invoking a third API corresponding to the result code indicative of the failed charge deduction to access the URL of the charge deduction failure notification page; and after the user terminal has accessed the URL, receiving data on the charge deduction failure notification page.
 16. The user terminal according to claim 10, wherein the processor is further configured to perform: in response to determining that the account identifier does not have the DND payment attribute, receiving a URL of a payment page from the third-party application server after the third-party application server receives a non-DND payment notification from the open network platform, the non-DND payment notification carrying a transaction identifier, a result code indicative of a non-DND payment, and the URL of the payment page; invoking a fourth API corresponding to the result code indicative of the non-DND payment to access the URL of the payment page; and after the user terminal has accessed the URL, sending a payment confirmation notification carrying the transaction identifier based on user input on the payment page displayed in the graphical user interface of the third-party application, such that the open network platform deducts a charge from the user account corresponding to the account identifier.
 17. The user terminal according to claim 16, wherein invoking the fourth API corresponding to the result code indicative of the non-DND payment comprises: rendering and displaying a second window in an upper layer on graphical user interface of the third-party application; and locking a layer lower than the second window on the graphical user interface, wherein only operation on the second window displayed on the upper layer is accepted by the user terminal until the second window is closed.
 18. The user terminal according to claim 10, wherein the processor is further configured to perform: sending a DND payment attribute setting request to the open network platform via the third-party application server, the DND payment attribute setting request carrying the account identifier and corresponding operation information received by the user terminal based on a user setting operation; wherein if the operation information indicates enabling a DND payment, the account identifier is recorded by the open network platform as the account identifier of the user account having the DND payment attribute; and if the operation information indicates canceling a DND payment, the account identifier is deleted by the open network platform from the account list of the recorded account identifiers having the DND payment attribute.
 19. A non-transitory computer-readable storage medium storing computer program instructions executable by at least one processor to perform: executing a third-party application on a graphical user interface; receiving a payment request of the virtual commodity based on a user input on the graphical user interface; sending the payment request to the open network platform via a third-party application server corresponding to the third-party application, the payment request carrying at least an account identifier such that the open network platform determines whether the account identifier has a Do Not Disturb (DND) payment attribute by querying an account list based on the account identifier; in response to determining that the account identifier has the DND payment attribute, receiving, from the open network platform via the third-party application server, a charge deduction result corresponding to a user account of the account identifier without receiving a payment page to be displayed that requests a user payment confirmation, the charge deduction result being obtained by directly deducting a charge from the user account corresponding to the account identifier on the open network platform; invoking an application programming interface (API) associated with the charge deduction result to render a first window of the charge deduction result; and displaying the first window in a floating layer on the graphical user interface associated with the third-party application such that user operations on the third-party application is not affected during a process of displaying the first window.
 20. The storage medium according to claim 19, wherein the computer program instructions further cause the at least one processor to perform: sending a DND payment attribute setting request to the open network platform via the third-party application server, the DND payment attribute setting request carrying the account identifier and corresponding operation information received by the user terminal based on a user setting operation; wherein: if the operation information indicates enabling a DND payment, the account identifier is recorded by the open network platform as the account identifier of the user account having the DND payment attribute; and if the operation information indicates canceling a DND payment, the account identifier is deleted by the open network platform from the account list of the recorded account identifiers having the DND payment attribute. 